Description

While test-integrating the patch set from #8307 I noticed that the patches were huge!

The functional change was miniscule though.

On investigation I discovered the patchset was huge because the unit test changes I made were showing up as diffs, because we have been shipping unit tests with our released packages for everything but functions and one other.

I made sure __tests__ was in .npmignore for all the packages (including a commit I tacked on the vertexai PR #8236) so those aren't shipped anymore and won't show up in package diffs when generating patch-package sets

While test-integrating this patch and auditing the resulting node_modules package contents I noticed 4 of the packages still shipped types tests as well. Added a second commit that ignores those

Related issues

Noticed in

• fix(crashlytics): avoid deprecation warning during correct API usage #8307

Release Summary

single conventional commit, but I did set it as a "fix" which will trigger a release since it affects the release artifacts

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • Yes
• My change supports the following platforms;
  • Android
  • iOS
• My change includes tests;
  • e2e tests added or updated in packages/\*\*/e2e
  • jest tests added or updated in packages/\*\*/__tests__
• I have updated TypeScript types that are affected by my change.
• This is a breaking change;
  • Yes
  • No

Test Plan

The patch-package set for this should result in removing the tests directories when applied while testing it

Think react-native-firebase is great? Please consider supporting the project with any of the below:

• 👉 Star this repo on GitHub ⭐️
• 👉 Follow React Native Firebase and Invertase on Twitter